| Package | hl7.terminology |
| Type | ValueSet |
| Id | Id |
| FHIR Version | R5 |
| Source | http://terminology.hl7.org/https://build.fhir.org/ig/HL7/UTG/ValueSet-v3-ActMoodRequest.html |
| Url | http://terminology.hl7.org/ValueSet/v3-ActMoodRequest |
| Version | 3.0.0 |
| Status | active |
| Date | 2014-03-26 |
| Name | ActMoodRequest |
| Title | ActMoodRequest |
| Experimental | False |
| Realm | uv |
| Authority | hl7 |
| Description | A request or order for a service is an intent directed from a placer (request author) to a fulfiller (service performer). *Rationale:* The concepts of a "request" and an "order" are viewed as different, because there is an implication of a mandate associated with order. In practice, however, this distinction has no general functional value in the inter-operation of health care computing. "Orders" are commonly refused for a variety of clinical and business reasons, and the notion of a "request" obligates the recipient (the fulfiller) to respond to the sender (the author). Indeed, in many regions, including Australia and Europe, the common term used is "request." Thus, the concept embodies both notions, as there is no useful distinction to be made. If a mandate is to be associated with a request, this will be embodied in the "local" business rules applied to the transactions. Should HL7 desire to provide a distinction between these in the future, the individual concepts could be added as specializations of this concept. The critical distinction here, is the difference between this concept and an "intent", of which it is a specialization. An intent involves decisions by a single party, the author. A request, however, involves decisions by two parties, the author and the fulfiller, with an obligation on the part of the fulfiller to respond to the request indicating that the fulfiller will indeed fulfill the request. |
| Copyright | This material derives from the HL7 Terminology THO. THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html |
No resources found
| CodeSystem | |
v3-ActMood  | ActMood |
Note: links and images are rebased to the (stated) source
Generated Narrative: ValueSet v3-ActMoodRequest
Language: en
FHIRhttp://terminology.hl7.org/CodeSystem/v3-ActMood where concept is-a RQO{
"resourceType" : "ValueSet",
"id" : "v3-ActMoodRequest",
"language" : "en",
"text" : {
"status" : "generated",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\" xml:lang=\"en\" lang=\"en\"><p class=\"res-header-id\"><b>Generated Narrative: ValueSet v3-ActMoodRequest</b></p><a name=\"v3-ActMoodRequest\"> </a><a name=\"hcv3-ActMoodRequest\"> </a><a name=\"v3-ActMoodRequest-en-US\"> </a><div style=\"display: inline-block; background-color: #d9e0e7; padding: 6px; margin: 4px; border: 1px solid #8da1b4; border-radius: 5px; line-height: 60%\"><p style=\"margin-bottom: 0px\">Language: en</p></div><ul><li>Include codes from<a href=\"CodeSystem-v3-ActMood.html\"><code>http://terminology.hl7.org/CodeSystem/v3-ActMood</code></a> where concept is-a <a href=\"CodeSystem-v3-ActMood.html#v3-ActMood-RQO\">RQO</a></li></ul></div>"
},
"url" : "http://terminology.hl7.org/ValueSet/v3-ActMoodRequest",
"identifier" : [
{
"system" : "urn:ietf:rfc:3986",
"value" : "urn:oid:2.16.840.1.113883.1.11.19947"
}
],
"version" : "3.0.0",
"name" : "ActMoodRequest",
"title" : "ActMoodRequest",
"status" : "active",
"experimental" : false,
"date" : "2014-03-26",
"publisher" : "Health Level Seven International",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://hl7.org"
},
{
"system" : "email",
"value" : "hq@HL7.org"
}
]
}
],
"description" : "A request or order for a service is an intent directed from a placer (request author) to a fulfiller (service performer).\r\n\r\n*Rationale:* The concepts of a \"request\" and an \"order\" are viewed as different, because there is an implication of a mandate associated with order. In practice, however, this distinction has no general functional value in the inter-operation of health care computing. \"Orders\" are commonly refused for a variety of clinical and business reasons, and the notion of a \"request\" obligates the recipient (the fulfiller) to respond to the sender (the author). Indeed, in many regions, including Australia and Europe, the common term used is \"request.\"\r\n\r\nThus, the concept embodies both notions, as there is no useful distinction to be made. If a mandate is to be associated with a request, this will be embodied in the \"local\" business rules applied to the transactions. Should HL7 desire to provide a distinction between these in the future, the individual concepts could be added as specializations of this concept.\r\n\r\nThe critical distinction here, is the difference between this concept and an \"intent\", of which it is a specialization. An intent involves decisions by a single party, the author. A request, however, involves decisions by two parties, the author and the fulfiller, with an obligation on the part of the fulfiller to respond to the request indicating that the fulfiller will indeed fulfill the request.",
"immutable" : true,
"copyright" : "This material derives from the HL7 Terminology THO. THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html",
"compose" : {
"include" : [
{
"system" : "http://terminology.hl7.org/CodeSystem/v3-ActMood",
"filter" : [
{
"property" : "concept",
"op" : "is-a",
"value" : "RQO"
}
]
}
]
}
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.